home *** CD-ROM | disk | FTP | other *** search
- Date: Wed, 1 Jun 1994 12:30:04 -0400 (EDT)
- From: Timothy Miller <millert@undergrad.csee.usf.edu>
- Subject: Re: Colour.
- To: gem-list@world.std.com
- In-Reply-To: <199406010451.AA247445050@relay2.geis.com>
- Message-Id: <Pine.3.87.9406011204.B2199-0100000@undergrad>
- Mime-Version: 1.0
- Precedence: bulk
-
-
-
- On Wed, 1 Jun 1994 s.sanders2@genie.geis.com wrote:
-
- > Reply: Item #5728781 from GEM-LIST-APPROVAL@WORLD.STD.COM@INET00#
- >
- > Timothy Miller:
- >
- > Actually, it would be better if the request could specify whether
- > a 'close' color was OK and to return the color if it actually got if
- > an exact request couldn't be honored. Likewise if the app demands a
- > specific color the call would fail if an exact match couldn't be
- > satisfied.
-
- I don't think it should fail. Since the app is going to have its own
- palette anyway, the manager should find the closest color and replace
- it. However, the problem with this is if more than one request ends up
- finding that the same palette entry is the closest for all of them,
- defeating the purpose. There should be facilities for supplying a
- partial palette and the manager makes necessary changes to the palette
- and reports back a list of entry numbers... this way, the manager
- wouldn't allow for two colors to end up accidentally in the same palette
- entry.
-
- >
- > Simon:
- >
- > I don't believe the user should be encouraged to edit .RSC files
- > under _any_ circumstances. If you want editable keyboard equivalents,
- > that's fine, just put it in the program as an option. That would
- > probably be less work and safer than scanning for key char names
- > anyway.
-
- I agree with this.
-
- >
- > -Scott @ SDS
- >
- >
- >
- >
-
-